software archaeologyの例文
- Software archaeology has continued to be a topic of discussion at more recent software engineering conferences.
- Like true archaeology, software archaeology involves investigative work to understand the thought processes of one's predecessors.
- Also, the missing availability of software and the associated source code can be a hindrance for software archaeology and research.
- There are still legitimate reasons for use in software archaeology, where the original disk drives are rarely available, and modern computers run too fast to preserve the delicate timing characteristics these techniques often relied on.
- Michael Rozlog of Embarcadero Technologies has described software archaeology as a six-step process which enables programmers to answer questions such as " What have I just inherited ? " and " Where are the scary sections of the code ? " These steps, similar to those identified by the OOPSLA workshop, include using visualization to obtain a visual representation of the program's design, using software metrics to look for design and style violations, using unit testing and profiling to look for bugs and performance bottlenecks, and assembling design information recovered by the process.
